-
Notifications
You must be signed in to change notification settings - Fork 747
feat(amazonq): client-side build support #6771
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
packages/core/src/codewhisperer/service/transformByQ/transformFileHandler.ts
Outdated
Show resolved
Hide resolved
|
The clear Problem/Solution description here is great! |
|
TODO: add change log entry EDIT: will merge behind a feature flag first, then add a change log entry in a future PR just before releasing |
| } | ||
|
|
||
| // TO-DO: remove when releasing CSB | ||
| export const isClientSideBuildEnabled = false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You'll notice there are a good amount of TO-DOs in this PR — the intention is to merge this feature behind a feature flag (this one), and simply enable everything in a future PR, once we are ready to release
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm tracking all TO-DOs to ensure when we release they are all addressed
|
/runIntegrationTests |
Problem
We should perform builds client-side (rather than server-side) to handle customers’ unique / challenging local environments, which often cause our server-side build to fail.
Solution
Periodically download intermediate
diff.patchfiles, apply them to a copy of the project, perform the local build, then upload the build logs and resume the transformation.feature/xbranches will not be squash-merged at release time.